-
Notifications
You must be signed in to change notification settings - Fork 572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JBPM-10199: Mark Async nodes as finished at the SVG when process inst… #3005
Conversation
Jenkins run fdb |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
@@ -144,8 +144,7 @@ public String getActiveProcessImage(String containerId, long procInstId, String | |||
fullLogs.stream() | |||
.filter(nodeInstanceDesc -> | |||
(((org.jbpm.kie.services.impl.model.NodeInstanceDesc) nodeInstanceDesc).getType() == NodeInstanceLog.TYPE_ASYNC_ENTER) && | |||
fullLogs.stream().noneMatch(nodeInst -> nodeInstanceDesc.getNodeId().equals(nodeInst.getNodeId()) | |||
&& (((org.jbpm.kie.services.impl.model.NodeInstanceDesc) nodeInst).getType() == NodeInstanceLog.TYPE_EXIT))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see this comment // Async active nodes don't have any related completed node instance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@domhanak before this change it only checked that the async node has an type_exit log to include it as an active one. Now it checks that it's not in the finished ones (including Exited, Aborted, Skipped and Obsolete) to be included as an active node and painted properly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! I am setting up rhpam to test the fix.
jenkins do fdb |
2 similar comments
jenkins do fdb |
jenkins do fdb |
@nmirasch My current end result is this: Could you please confirm this is expected? I am a bit confused as the issue states the Human Task should have Blue Borders but it doesn't. Another thing I noticed is a strange behavior with 2 async nodes in succesion: From my side it looks good, the aborted process is on End Node and that makes sense. |
@domhanak the weird result that I wasn't able to reproduce, is that blue border color (active nodes) after aborting the instance. I tried aborting it via rest and from the BC with the same results, no blue color anywhere. The expected node colors at the diagram are:
|
@nmirasch Okay, I will give it another go and let you know. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have confirmed with @nmirasch that this blue bordrer
on End state is not related and seems to be a separate issue. After fresh install, I am unable to reproduce it again.
Apologies for the weird issues report but I was able to do reproduce it consistently and did so several times before posting here :D
Approved.
thanks @domhanak ! |
…ance is aborted (#3005)
…ance is aborted (#3005)
…ance is aborted (#3005) (#3022) Co-authored-by: nmirasch <[email protected]>
…ance is aborted (#3005) (#3023) Co-authored-by: nmirasch <[email protected]>
…ance is aborted
jira:https://issues.redhat.com/browse/JBPM-10199
How to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.
How to retest this PR or trigger a specific build:
a pull request please add comment: Jenkins retest this
a full downstream build please add comment: Jenkins run fdb
a compile downstream build please add comment: Jenkins run cdb
a full production downstream build please add comment: Jenkins execute product fdb
an upstream build please add comment: Jenkins run upstream
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>
, where<branch-name>
is the name of the branch where the pull request must be backported to (e.g.,backport-7.67.x
to backport the original PR to the7.67.x
branch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.